Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference
763-tree-1
name
1102
tree-preservation-order

undefined

763-tpo-1
uprn
address-text
point
POINT (-1.010748 50.886679)
geometry
MULTIPOLYGON (((-1.010720 50.886676,-1.010721 50.886681,-1.010725 50.886686,-1.010739 50.886693,-1.010748 50.886694,-1.010765 50.886691,-1.010771 50.886687,-1.010775 50.886682,-1.010777 50.886676,-1.010776 50.886671,-1.010772 50.886666,-1.010766 50.886662,-1.010758 50.886659,-1.010749 50.886658,-1.010732 50.886661,-1.010726 50.886665,-1.010722 50.886670,-1.010720 50.886676)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL